Software User's Guide Version 3.3

Using the Software

This chapter describes how to use the software. It consists of:

Entering Commands
Connecting to a Process
Some Configuration Suggestions
Accessing the Second-Level Processes
Accessing the Third-Level Processes
"Command Completion"
Command History

Entering Commands

When typing a command, remember the following:

You may type only enough sequential letters of the command to make it unique among the available commands. For example, to execute the reload command you must enter rel as a minimum. The minimum number of required characters are underlined in the command syntax chapters.
Commands are not case-sensitive.
Sometimes, only the first letter of the command (and subsequent options) is required to execute the command. For example, typing s at the * prompt followed by pressing the Enter key causes the status command to be executed.
When command completion is enabled, you can press Esc and enter ? to obtain help on entering commands. See "Command Completion" and "Command History" for more information.

When you start the device, the console displays a boot message. The OPCON prompt (*) then appears on the screen indicating that you are in the OPCON process and you can begin entering OPCON commands. This is the command prompt from which you communicate with different processes.

Commands that are needed more often appear before the "- - - - -" separator. Enter the appropriate command at the OPCON prompt (*). See Table 3 for a list of commands.

Alternatively, you can:

Find out the process ID (PID) number of a process by entering the status command at the * prompt.

The status command displays information about the device processes, such as the process IDs (PIDs), process names and status of the process. Issuing the status command is shown in the following example:

     * status
     Pid  Name      Status TTY  Comments
     1    COpCn1    RDY    TTY0
     2    Monitr    DET     --
     3    Tasker    RDY     --
     4    MOSDBG    DET     --
     5    CGWCon    DET     --
     6    Config    DET     --
     7    Ezystrt   IDL     --
     8    ROpCn1    IDL    TTY1 128.185.210.125
     9    ROpCn2    IDL    TTY2
     10   CES3      IDL     --
     11   TOUT      IDL     --
     12   L2S3      RDY     --
     13   L3L2      RDY     --
     14   LLL2      RDY     --
     15   S3CE      RDY     --

Use the talk pid command, where pid is the number of the process to which you want to connect. (For more information about these and other OPCON commands, refer to "What is the OPCON Process?".)
Note: Not every process listed has a user interface (for example, the talk 3 process). The talk 4 command is for use by your service representatives.

Identifying Prompts

Each process uses a different prompt. You can tell which process your console is connected to by looking at the prompt. (If the prompt does not appear when you enter the talk pid command, press Enter again.)

The following list shows the prompts for the five main processes:

Table 1. Processes, Their Purpose, and Commands to Access

Process Level and Purpose Command to Access Input Prompt
OPCON Level 1 - access to all secondary levels Ctrl-P asterisk (*)
CONFIG Level 2 - base services configuration and access to configuration third level Configuration or talk 6 Config >
GWCON Level 2 - base services operation and monitoring and access to operations and monitoring on third level Console or talk 5 plus sign (+)
MONITR Level 2 - message display Event or talk 2 (none)
MOSDBG Level 2 - diagnostic environment talk 4 $

Note: Only enter the talk 4 command under the direction of a service representative.

At the OPCON prompt level, you can begin to enter commands from the keyboard. Use the Backspace key to delete the last character typed in on the command line. Use Ctrl-U to delete the whole command line entry so that you can reenter a command. See "Command Completion" and "Command History" for additional details or press Escape ?.

Getting Help

At the command prompts, you can obtain help in the form of a listing of the commands available at that level. To do this, type ? (the help command), and then press Enter. Use ? to list the commands that are available from the current level. You can usually enter a ? after a specific command name to list its options.

Exiting a Lower Level Environment

The multiple-level nature of the software places you in secondary, tertiary, and even lower level environments as you configure or operate the 2210. To return to the next higher level, enter the exit command. To get to the secondary level, continue entering exit until you receive the secondary level prompt (either Config> or +).

For example, to exit the ASRT protocol configuration process:

ASRT config> exit
Config>

If you need to get to the primary level (OPCON), enter the intercept character (Ctrl-P by default).

Getting Back to OPCON

To get back to the OPCON prompt (*), press Ctrl-P. You must always return to OPCON before you can communicate with another process. For example, if you are connected to the console (GWCON) process and you want to connect to the CONFIG process, you must press Ctrl-P to return to OPCON first. The Ctrl-P key combination is the default intercept character.

If you use the intercept character from a third-level or lower level menu to return to the * prompt, the next time you use the talk command to talk to the same process, you will reenter that same level menu. This link goes away when the device is re-initialized.

Some Configuration Suggestions

Configuring a 2210 is different depending on whether you are configuring for the first time, creating a configuration based on an existing configuration, or just updating a configuration. Use the following sections as a guide to the best procedure to use, depending on your needs.

Creating a First Configuration

This procedure assumes that you have no other 2210 that contains a configuration similar to the one for the 2210 you are configuring. The procedure also assumes that you have just taken the 2210 out of the box. Although this procedure specifies an order, you can perform the actual configuration (after step 3) in any order.

To configure a IBM 2210 for the first time:

Examine the 2210 you are configuring to determine which interfaces you need to configure. Note these for later use.
Connect to the 2210 as described in Accessing the Software Using Local and Remote Consoles.
Initially configure a port on the 2210 and at least an internal IP address for the device using Quick Config as described in Quick Configuration or Appendix A, Quick Configuration Reference. Configure the minimum needed to allow you to Telnet into the device.
Configure any base services, such as boot options. Access the configuration process as described in Accessing the Configuration Process, CONFIG (Talk 6).
Configure the interfaces. Access the interface configuration process as described in Accessing the Network Interface Configuration Process.
Configure any required features. Access the feature configuration process as described in Accessing Feature Configuration and Operating Processes.
Configure any protocols that will run through this device. Access the protocol configuration process as described in Accessing Protocol Configuration and Operating Processes.
Note: At the very least, you will configure IP in this step.
Restart the device as described in Reloading or Restarting the Device.

Basing a Configuration on an Existing Configuration

This section describes how to:

Base a configuration on the configuration in an operating 2210
Permanently update the configuration in a 2210
Temporarily update the configuration of a 2210 while the 2210 is operating

Basing on an Existing Configuration

If you already have a 2210 that has the same interfaces, features, and protocols that you want to configure on a new 2210, you can save time by basing the configuration on the existing 2210. You can perform this type of configuration either using the command line interface or by using the configuration program that comes with the 2210. In both cases, the procedures assume that the 2210 is not in your production network.

To base a configuration on an existing configuration using the command line interface:

Obtain a copy of the configuration you want to use.
1. Enter talk 6 at the OPCON (*) prompt.
2. Enter boot at the Config> prompt.
3. Enter the copy command at the Boot config> prompt. See The Boot CONFIG Process for more information.
Connect to the 2210 that you are configuring.
Load the configuration you obtained in step 1 into the 2210 using TFTP GET. See The Boot CONFIG Process.
Update the configuration.
Restart the 2210.

To base a configuration on an existing configuration using the configuration program:

Start the configuration program.
Retrieve the configuration from the 2210 on which you want to base the new configuration.
Make the changes you need for the new configuration. These changes include addresses, the host names, users, and other items.
Save the configuration with a different name from the name that you used to retrieve the configuration.
Send the configuration to the 2210 you are configuring.
Restart the 2210.

For more about using the configuration program, see Configuration Program User's Guide for Nways Multiprotocol and Access Services Products.

Permanently Updating a Configuration

To permanently update a configuration:

Access the 2210 you are updating as described in Accessing the Software Using Local and Remote Consoles. You will see the * prompt.
Enter the talk 6 command to access the configuration process.
Enter the appropriate commands to access the third-level process that configures the areas that you are changing.
Enter exit as many times as needed to return to the configuration process.
Restart the 2210.

Temporarily Updating a Configuration

The ability to temporarily update a configuration allows you to make changes to some of the operating characteristics of a 2210 until you can make permanent updates to the configuration. This enables you to implement changes immediately to resolve problems or improve performance and avoid an outage during a peak period. You can then make permanent updates to the configuration and schedule an outage so you can restart to pick up the change.

To temporarily update a configuration:

Access the 2210 you are updating as described in Accessing the Software Using Local and Remote Consoles. You will see the * prompt.
Enter the talk 5 command to access the operating/monitoring process.
Note: Not all interface types, protocols, or features allow you to make temporary config changes via talk 5 commands.
Enter the appropriate commands to access the third-level process that monitors the areas that you are changing.
Enter exit as many times as needed to return to the operating/monitoring process.
Enter Ctrl-P to return to the * prompt.
Exit the device as described in Exiting the Device

Accessing the Second-Level Processes

All interfaces, features, and protocols have commands that you use to access the following processes:

The configuration process to initially configure and enable the interface, feature, or protocol, as well as perform later configuration changes.
The operating/monitoring process to display information about each interface, feature, or protocol, to make temporary configuration changes, or to activate configuration changes.

You can also configure or operate some base system services through the second-level processes. The commands to perform these functions are described starting in What is CONFIG?.

The next sections describe the procedures for accessing the second-level processes.

Accessing the Configuration Process, CONFIG (Talk 6)

Each protocol configuration process is accessed through the device's CONFIG process. CONFIG is the second-level process of the device user interface that lets you communicate with third-level processes. Protocol processes are examples of third-level processes.

The CONFIG command interface is made up of levels of menus. Protocol configuration command interfaces are menus within the CONFIG interface. Each protocol configuration interface has its own prompt. For example, the prompt for the SNMP protocol command interface is SNMP config>.

The next sections describe these procedures in more detail.

Entering the CONFIG Process

To enter the CONFIG process from OPCON and obtain the CONFIG prompt, enter the configuration command. Alternatively, you can enter the OPCON talk command and the PID for CONFIG. The PID for CONFIG is 6.

* configuration

* talk 6

The console displays the CONFIG prompt (Config>). If the prompt does not appear, press the Enter key again.

Quick Configuration Process

Quick Configuration, or Quick Config, allows you to quickly configure portions of the device without dealing with the specific operating system commands. You enter the Quick Config menus from the CONFIG process using the qconfig command (see Quick Configuration).

Restarting or Reloading the Device

Changes that you make to the protocol parameters through CONFIG do not take effect until you either activate the net that contains any dynamic changes or the device software.

To restart the device, enter the OPCON restart command. For example:

* restart

Are you sure you want to restart the device? (Yes or No): yes

Accessing the Console Operating/Monitoring Process, GWCON (Talk 5)

To view information about the interfaces, features, or protocols or to change parameters while running, you must access and use the operating (monitoring) process. Operating command interfaces are modes of the GWCON interface. Within the GWCON mode, each interface, feature, or protocol interface has its own prompt. For example, the prompt for the SNMP protocol is SNMP>.
Note: Any parameters you change in this process will not remain active across any event that causes the 2210 to reload the operational code, such as a power outage or entering the restart command.

The next sections describe these procedures in more detail.

Entering the GWCON Command Process

To enter the GWCON process from OPCON and obtain the GWCON prompt, enter the console command. Alternatively, you may enter the talk command and the PID for GWCON. The PID for GWCON is 5. For example:

* console

* talk 5

The GWCON prompt (+) then displays on the console. If the prompt does not appear, press Enter again.

Accessing the Third-Level Processes

After accessing the second level, you must enter commands on the third level to configure or operate the interfaces, features, and protocols in your IBM 2210. The following sections describe how to access the third level processes.

Adding Devices

This section describes how to use the add device command to configure the network interfaces. A network interface is usually an adapter, but it can also be a definition used by an operating process. For example, two IP addresses can be assigned to one port and each one is considered an interface. After you establish an interface using the add device command, you can access the network interface configuration and operating processes, for example, the Talk 5 monitoring processes. These processes are used to change and monitor the software-configurable parameters for the network interfaces that are used in your device.

Accessing the Network Interface Configuration Process

Use the following procedure to access the device's configuration process. This process gives you access to a specific interface's configuration process.

At the OPCON prompt, enter the configuration command.
```
* configuration
```
After you enter the configuration command, the CONFIG prompt (Config>) displays on the console. If the prompt does not appear when you first enter configuration, press Enter again.
Use the add device command to create a network interface. The add device command automatically assigns the interface number. (Enter add device ? to get a list of the supported device types.)
These are the types of devices that are supported:
1. Dial circuits
  The following example adds a dial circuit interface:
```
   Config> add device dial-circuit
   Enter the number of PPP Dial Circuit interfaces [1]?
   Adding device as interface 8
   Base net for this circuit[0]?4
   Defaulting Data-link protocol to PPP
   Use "set data-link" command to change the data-link protocol
   Use "net 8" command to configure circuit parameters 
```
2. The following example adds a dial-in circuit:
```
Config>add device dial-in
Enter the number of dial-in interfaces [1]?
Adding device as interface 5
Base net for this circuit [0]? 5
Defaulting Data-link protocol to PPP
Use "set data-link" command to change the data-link protocol
Use "net 5" command to configure circuit parameters
```
3. The following example adds a dial-out circuit:
  Note: The dial-out device type is only supported if the software load includes the DIALs feature.
```
Config>add device dial-out*
Enter the number of dial-out interfaces [1]?
Adding device as interface 6*
Base net for this circuit [0]? 4
Defaulting Data-link protocol to Dial-out*
Use "net 6" command to configure circuit parameters*
 
```
4. Multilink PPP
  The following example adds a multilink PPP interface:
```
Config>add device multilink-ppp
Enter the number of Multilink PPP interfaces [1]?
Adding device as interface 7
Defaulting Data-link protocol to PPP
Use "net 7" command to configure circuit parameters
```
Notes:
1. Interfaces are automatically created for the base ports and ports on an adapter inserted into the feature slot for those models that have a feature slot, so you only need to use the add device command to create virtual interfaces. The examples below show the types of virtual interfaces that can be added.
2. When you create interfaces for serial adapters or dial circuits, the default data-link type is PPP. However, you can use the set data-link command to change the data-link type. Refer to Table 2 for the data-link types supported on serial ports and dial circuits, and to the description of the set data-link command on page ***.

At the Config> prompt, enter the list devices command to display the network interface numbers for which the device is currently configured, as follows:

Config> list devices
 
Ifc 0 Ethernet                        CSR  81600, CSR2  80C00, vector 94
Ifc 1 WAN X.25                        CSR  81620, CSR2  80D00, vector 93
Ifc 2 WAN X.25                        CSR  81640, CSR2  80E00, vector 92
Ifc 3 WAN PPP                         CSR 381620, CSR2 380D00, vector 125
Ifc 4 WAN Frame Relay                 CSR 381640, CSR2 380E00, vector 124
Ifc 5 Token Ring                      CSR 600000, vector 95

Record the interface numbers.
Enter the CONFIG network command and the number of the interface you want to configure. For example:
```
Config> network 1
 
```
The appropriate configuration prompt (such as TKR Config> for token-ring), now displays on the console.

Note:

Not all network interfaces are user-configurable. For interfaces that cannot be configured, you receive the message:

     That network is not configurable

Displaying the Interface Configuration

From the same interface configuration prompts, you can list configuration information specific to that selected interface by using the list command. For example:

     TKR Config> list
 
     Token-Ring configuration:
 
     PACKET SIZE (INFO FIELD): 4472
     Speed:                    16 Mb/sec
     Media:                    Shielded
 
     RIF Aging Timer:          120     Source Routing:           Enabled
     MAC Address:              000000000000

Configuring the Network Interface

Refer to the specific chapters in this guide for complete information on configuring your IBM 2210's network interfaces.

Table 2 lists network architectures and the supported interfaces for each architecture.

Table 2. Network Architecture and the Supported Interfaces

Network Architecture Supported Interfaces
ATM Dual Port Serial Interface (25 Mbps) for IBM 2210
802.5 Token-Ring IBM 2210 Token-Ring 4/16 Interface
Ethernet IBM 2210 Ethernet Interface
ISDN Serial Interfaces for IBM 2210 as follows:

Basic Rate Interface (BRI)
PRI/Channelized T1/J1 Interface *
PRI/Channelized E1 Interface *

Notes:

The interfaces marked with an asterisk (*) can be used either as ISDN or channelized interfaces.

Note:

Point-to-Point Serial Interface for IBM 2210, dial circuit interface; supported on 4-port and 8-port WAN concentration adapters
Frame Relay Serial Interface for IBM 2210, dial circuit interface; supported on 4-port and 8-port WAN concentration adapters
X.25 Serial Interface for IBM 2210; supported on 4-port and 8-port WAN concentration adapters and dial circuits
SDLC Relay Serial Interface for IBM 2210; supported on 4-port and 8-port WAN concentration adapters
Bisync Serial Interface for IBM 2210; supported on 4-port and 8-port WAN concentration adapters
SDLC Serial Interface for IBM 2210; supported on 4-port and 8-port WAN concentration adapters and dial circuits
V.25bis Serial Interface for IBM 2210; supported on 4-port and 8-port WAN concentration adapters
V.34 Serial Interface for IBM 2210; supported on 4-port and 8-port WAN concentration adapters and 4-port and 8-port Dial Access adapters.
Dial-Out Supports DIALs and Telnet dial-out over V.34 base interfaces
Dial-In A PPP dial circuit interface that has configuration parameters defaulted to support DIALs
Multilink PPP (MP) Supported on any PPP link
L2TP, L2F, and PPTP Supports virtual PPP DIALs connections through the Layer 2 Tunneling Protocol (L2TP), Layer 2 Forwarding (L2F), and Point to Point Tunneling Protocol (PPTP).

Notes:

PPP dial circuit interfaces can use ISDN, a V.34 network, or V.25bis as the base network interface.
FR dial circuit interfaces can use an ISDN or a V.25bis network as the base network interface.
Dial-Out circuit interfaces use a V.34 network as the base network interface.
Dial-In circuit interfaces can use an ISDN or V.34 network as the base network interface.
SDLC dial circuits use V.25bis as the base network interface.
X.25 uses the ISDN BRI D-channel as the base network interface.

Accessing the Network Interface Console Process

To monitor information related to a specific device, access the console process by using the following procedure:

At the OPCON prompt, enter the console command . For example:
```
* console
```
The GWCON prompt (+) is displayed on the console. If the prompt does not appear when you first enter GWCON, press Enter again.

At the GWCON prompt, enter the configuration command. For example:

+ configuration
 
Multiprotocol Routing Services
2210-MRS Feature 3768 V3.2 Mod 0 PTF 0 RPQ 0 MRS.E00 cc4_2a  
Boot ROM version  1.20     Watchdog timer enabled    Auto-boot enabled
 
Time: 13:34:56    Thursday     March 9, 1995       Console baud rate: 9600
 
Num Name  Protocol
0   IP    DOD-IP
3   ARP   Address Resolution
11  SNMP  Simple Network Management Protocol
12  OSPF  Open SPF-Based Routing Protocol
23  ASRT  Adaptive Source Routing Transparent Enhanced Bridge
 
Num Name  Feature
1   BRS   Bandwidth Reservation
2   MCF   MAC Filtering
 
3 Networks:
Net Interface  MAC/Data-Link         Hardware         State
0   Eth/0      Ethernet/IEEE 802.3   SCC Ethernet     Up
1   PPP/0      Point to Point        SCC Serial Line  Up
2   PPP/1      Point to Point        SCC Serial Line  UP

Enter the GWCON network command and the number of the interface you want to monitor. For example:
```
+ network 2 
X.25>
```
In this example, the X.25 console prompt is displayed on the console. You can then view information about the X.25 interface by entering the X.25 console commands.

Monitoring the Network Interface

Refer to the specific chapters in this manual for complete information on monitoring your 2210's network interfaces.

Accessing Feature Configuration and Operating Processes

To help you access the Multiprotocol Routing Services feature configuration and operating processes, this section outlines both of these procedures.

Accessing the Feature Processes

Use the feature command from the CONFIG process to access configuration commands for specific Multiprotocol Routing Services features outside of the protocol and network interface configuration processes.

Use the feature command from the GWCON process to access console commands for specific features that are outside of the protocol and network interface console processes.

Enter a question mark after the feature command to display a listing of the features available for your software release. For example:

     Config> feature ?
 
     WRS
     BRS
     MCF
     
     Feature name or number [1] ?

To access a particular feature's configuration or operating prompt, enter the feature command at the Config> or + (GWCON) prompt, respectively, followed by the feature number or short name. For example:

     Config> feature mcf
 
     MAC filtering user configuration
 
     Filter Config>

Table 7 lists the available feature numbers and names.

Once you access the configuration or operating prompt for a feature, you can begin entering specific commands for the feature. To return to the previous prompt level, enter the exit command at the feature's prompt.

Accessing Protocol Configuration and Operating Processes

This section describes how to access the protocol configuration and operating processes.

Entering a Protocol Configuration Process

To enter the desired protocol configuration process from the CONFIG> prompt:

At the CONFIG> prompt, enter the list configuration command to see the numbers and names of the protocols purchased in your copy of the software. See page *** for sample output of the list configuration command.
From the Config> prompt, enter the protocol command with the number or short name (for example, SNMP) of the protocol you want to configure. The protocol number and short name is obtained from the list configuration command display. In the following example, the command has been entered for accessing the SNMP protocol configuration process:
```
Config> protocol SNMP
```
or
```
Config> protocol 11
SNMP user configuration
 
```
The protocol configuration prompt then displays on the console. The following example shows the SNMP protocol configuration prompt:
```
SNMP config>
```

You can now begin entering the protocol's configuration commands. See the corresponding protocol section of the Protocol Configuration and Monitoring Reference for more information on specific protocol configuration commands.

In summary, the protocol command lets you enter the configuration process for the protocol software installed in your device. The protocol command enters a protocol's command process. After entering the protocol command, the prompt of the specified protocol appears. From the prompt, you can enter commands specific to that protocol.

Entering a Protocol Operating Process

To enter a protocol console process from the GWCON prompt:

At the GWCON prompt, enter the configuration command to see the protocols and networks configured for the device. For example:

+configuration
 
Multiprotocol Routing Services
2210-MRS Feature 3768 V3.2 Mod 0 PTF 0 RPQ 0 MRS.E00 cc4_2a  
Boot ROM version  1.10     Watchdog timer enabled    Auto-boot enabled
Time: 13:43:04    Thursday     March 9, 1995       Console baud rate: 9600
 
Num Name  Protocol
0   IP    DOD-IP
3   ARP   Address Resolution
7   IPX   Netware IPX
11  SNMP  Simple Network Management Protocol
12  OSPF  Open SPF-Based Routing Protocol
23  ASRT  Adaptive Source Routing Transparent Enhanced Bridge
26  DLS   Data Link Switching
 
Num Name  Feature
1   BRS   Bandwidth Reservation
2   MCF   MAC Filtering
 
3 Networks:
Net Interface  MAC/Data-Link         Hardware            State
0   TKR/0      Token-Ring/802.5      IBM Token-Ring      Up
1   FR/0       Frame Relay           SCC Serial Line     Down
2   PPP/0      Point to Point        SCC Serial Line     Up

Enter the GWCON protocol command with the protocol number or short name of the desired protocol displayed in the configuration information.
In the following example, the command has been entered for accessing the SNMP protocol console process.
```
+ protocol 11
```
or
```
+ protocol SNMP
```
The protocol console prompt then displays on the console. This example shows the SNMP protocol console prompt:
```
SNMP>
```

You can now begin entering the protocol's commands. See the corresponding protocol section of the Protocol Configuration and Monitoring Reference for more information on specific protocol console commands.

Command Completion

The automatic command completion function assists you with the syntax for commands entered at the command line.

To illustrate the behavior of Command Completion, assume that the following commands are allowed in a given menu context. (This is an example menu only.)

enable

auto-refresh

caching

set

cache-size

cache-timeout

priority

If you type ena and press the Space Bar, the full command is shown as ENABLE. If you now type ?, a list of possible items to enable are shown (auto-refresh and caching) and the command ENABLE remains on the command line.
If you type ena and press Enter, a message is printed that the command is not fully specified, and a list of possible items to enable are shown (auto-refresh and caching) and the command ENABLE remains on the command line.
Because the ENABLE command requires an item to enable, it appears in a list of possible command completions with "..." in the left margin to indicate that more input is required for the command.
If your input matches multiple commands, a list of possible completions is displayed. Your input on the new command line is expanded to the longest common prefix. For example, if you enter set ca, and then press the space bar, CACHE-SIZE and CACHE-TIMEOUT will be listed, and the new command line will be expanded to SET cache-, since "cache-" is common to both possible completions. Now you must type the letter "s" or the letter "t" to distinguish between the possible completions "size" or "timeout".
Common commands sometimes appear in an alternate form (SHOW, DISPLAY, LIST). If the Command Completion does not yield a match on a common command, such as SHOW, the alternatives DISPLAY or LIST will be displayed, if found.
If the search for a command (and alternatives) does not yield an exact match, you are presented with a list of possible completions, using some portion of your input. For example, enanle followed by the Space Bar would be replaced with ena and ENABLE would be listed as the possible completion.
When a list of possible commands is shown, you can use the Tab key to cycle through one command at a time on the current command line. You can use the Space Bar or Enter key to select the command shown.

Online Help When Command Completion is Enabled

The following online help is available when command-completion is enabled.

See page *** for the enable command-completion syntax.

?: Question mark displays a list of possible completions. A message appears if the command is already complete.
Space Bar: Attempts to complete the current word on the command line. If a unique match is not found, possible completions are listed.
Tab: Attempts to complete the current word on the command line. If a unique match is not found, possible completions are listed and you may cycle through these possible completions using the Tab key. Use the Space Bar or the Enter key to select the currently displayed command.
Enter: Attempts to complete the current word on the command line. If the command is complete, Enter executes the command and stores it in the Command History. If the command is incomplete, a list of possible completions is displayed.
Ctrl-P: Returns to the MOS Operator Console prompt (*). (Ctrl-P is the default Intercept Character.)
Backspace: Deletes the last character on the command line.
Ctrl-W: Deletes the last word on the command line.
Ctrl-U: Aborts the current command.
Ctrl-L: Refreshes the current command line to display its contents.
Ctrl-B: Retrieve Backward. Replaces the current command line with the previous command in the circular Command History.
Ctrl-F: Retrieve Forward. Replaces the current command line with the next command in the Command History.
Ctrl-R: Marks the start of a Repeat Sequence in the Command History. Use with the Ctrl-N function.
Ctrl-N: Replaces the current command line with the next command in the Repeat Sequence whose starting command was marked with Ctrl-R.
Ctrl-C: Cancels Easy-Start, if active.
Escape ?: Escape, followed by "?" prints this Command Line Help:

The following rules apply to automatic command completion:

Completed commands are shown in UPPERCASE on the command line.
Common commands sometimes appear in an alternate form (ADD versus CREATE). If the command completion does not yield a match on a common command, any alternative commands will be displayed.
If the search for a command (and alternative commands) does not yield a unique match, a list of possible completions is shown, and the longest common prefix is presented.
When possible completions are listed, commands requiring further command input are shown with "..." in the left margin.
When a Command History retrieve key (Ctrl-B,F,N) is pressed, the Command History is scanned for a command that successfully parses in the current command context. A tone will be sounded if no such command exists.
Some command menus are built dynamically. Command Completion cannot always follow these dynamic links. '?' can be entered in these cases.
To disable Command Completion for just one command (to enter a comment), type any Comment Character as the first character on the command line. The Comment Characters are !@#$%*:;/'"
Command Completion will be disabled in the event of an internal error. Report the Debug information on the screen to Customer Support.
Command Completion is currently Enabled. To Disable this option, use the disable command-completion command from Configuration talk 6.

Online Help When Command Completion is Disabled

The following online help is available when command-completion is disabled:

?: When a ? (Question Mark) is entered at the end of the command line, a list of possible completions is shown.
Enter: Executes the command and stores it in the Command History. A message is printed if the command is not fully specified
Ctrl-P: Returns to the MOS Operator Console prompt (*). (Ctrl-P is the default Intercept Character.)
Backspace: Deletes the last character on the command line.
Ctrl-U: Aborts the current command.
Ctrl-B: Retrieve Backward. Replaces the current command line with the previous command in the circular Command History.
Ctrl-F: Retrieve Forward. Replaces the current command line with the next command in the Command History.
Ctrl-R: Marks the start of a Repeat Sequence in the Command History. Use with the Ctrl-N function.
Ctrl-N: Replaces the current command line with the next command in the Repeat Sequence whose starting command was marked with Ctrl-R.
Ctrl-C: Cancels Easy-Start, if active.
Escape ?: Escape, followed by "?" prints this Command Line Help:

Command Completion is currently Disabled.  To Enable this option,
use the enable command-completion command from Configuration talk 6.

Command History

The Command History contains up to the last 20 commands entered by the user in OPCON, GWCON (Talk 5) or CONFIG (Talk 6) command line menus.

Backward and Forward retrieve keys can be used to recall previously entered commands. In addition, a facility is provided to enable the advanced user to repeat a particular series of commands.

Repeating a Command in the Command History

By pressing Ctrl-B (backward) or Ctrl-F (forward) at any command line prompt in an OPCON, GWCON or CONFIG menu, the current command line is replaced by the previous or next command in the Command History. The Command History is common across the command line interface. That is, a command entered while in a GWCON menu can be retrieved from within CONFIG and a command entered while in a CONFIG menu can be retrieved from within GWCON.

When automatic Command Completion is enabled (See"Command Completion") and a Command History retrieve key (Ctrl-B,F,N) is pressed, the Command History is scanned for a command that successfully parses in the current command context. A tone will be sounded if no such command exists.

The Command History contains the most recently entered commands, up to a maximum of the last 20 commands. If only three commands have been entered since a restart, pressing Ctrl-F or Ctrl-B circles through only those three commands. If no commands have been entered thus far, Ctrl-F or Ctrl-B results in tone sound.
Note: A command aborted by pressing Ctrl-U will not be entered into the Command History. When Command Completion is enabled, only complete commands are entered into the Command History.

To enter two similar commands:

display sub les

display sub lec

Enter:

display sub les, then press Enter

Ctrl-B for Backward, and the current line is replaced with-

display sub les

Press Backspace and replace "s" with "c" to get

display sub lec and then press Enter

Repeating a Series of Commands in the Command History

There is an additional feature for advanced users to facilitate repeating a particular series of GWCON or CONFIG commands. C1, C2,...,Cn in the Command History is referred to as a repeat sequence. This feature may be more convenient than simply using Ctrl-B and Ctrl-F when you must repeat a given task that requires multiple commands. Enter Ctrl-R (repeat) to set the start of the repeat sequence at command C1. Enter Ctrl-N (next) successively to retrieve the next command in the repeat sequence. Commands are not automatically entered, but are placed on the current command line allowing you to modify or enter the command.

To produce the desired behavior of a repeat sequence, the first command retrieved using the first Ctrl-N (next) depends on the manner in which the start of the repeat sequence was set using Ctrl-R (repeat).

Setting the start of the repeat sequence with Ctrl-R can be done in two ways:

When C1 is initially entered
When C1 is retrieved from the Command History with Ctrl-B or Ctrl-F.

Starting a Repeat Sequence As Commands Are Entered

If you enter Ctrl-R as command C1 is being keyed in, and then enter commands C2, C3... Cn. Ctrl-N will successively bring commands C1, C2, ... Cn, C1, C2, ... Cn, C1, ... to the command line.

In Example 1, the start of the repeat sequence is set as the first command is keyed in. The user knows ahead of time that the same commands to be entered in GWCON need to be repeated in CONFIG.

Example 1

As the first command in the sequence is keyed in, use Ctrl-R (repeat) to set the start of the repeat sequence.
```
  *console
  +event Ctrl-R 
```
then press Enter to set the start of the repeat sequence.

Continue typing the subsequent commands in the sequence:

Event Logging System user console
  ELS>display sub les
  ELS>display sub lec
  ELS>exit
  +

To enter these same commands in CONFIG, press

Ctrl-P (the default OPCON intercept character) and go to CONFIG.

  +-press Ctrl-P-
  *configuration
  Config>Ctrl-N for NEXT to retrieve the start of this sequence-
  Config>event Enter
  Event Logging System user configuration
  ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
  ELS config>display sub les Enter
  ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
  ELS config>display sub lec Enter
  ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
  ELS config>exit Enter
  Config>

Starting a Repeat Sequence After All Commands Are Entered

On the other hand, if you first enter C1, C2, ... Cn, and retrieve C1 via Ctrl-B or Ctrl-F. Entering Ctrl-R, entering Ctrl-N successively brings commands C2,..., Cn, C1, C2,..., Cn, C1,...,Cn to the command line (see Example 2). The first occurrence of C1 is bypassed since C1 is already available on the command line at the time it was retrieved, and does not need to be recalled again by the first Ctrl-N.

In Example 2, all the commands are entered and then the first command in the sequence to be repeated is retrieved. A sequence of commands has been entered in GWCON, and the same sequence needs to be repeated in CONFIG.

Example 2

Enter the following commands in GWCON:

 *console
 +event
 Event Logging System user console
 ELS>display sub les
 ELS>display sub lec
 ELS>exit
 +

To enter these same commands in CONFIG, press Ctrl-P (the default OPCON intercept character) and go to CONFIG.

 +Ctrl-P-
 *configuration
 Config>Ctrl-B four times to retrieve the start of
         the four command sequence in this example-
 Config>event
 Config>event Ctrl-R for REPEAT to set the start of the repeat sequence-
  Config>event Enter
  Event Logging System user configuration
  ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
  ELS config>display sub les Enter
  ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
  ELS config>display sub lec Enter
  ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
  ELS config>exit Enter
  Config>

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]